[hotfix] Miscellaneous fixes on GHA workflows #3839
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ping @leonardBang |
yuxiqian
force-pushed
the
misc/workflow-update
branch
from
2520f5e to
303a6e9
Compare
|
Thanks @yuxiqian for considering the newly-added maxcompute label, nice work |
leonardBang
approved these changes
Jan 8, 2025
yuxiqian
force-pushed
the
misc/workflow-update
branch
from
303a6e9 to
60f9db4
Compare
|
Seems MaxCompute unit tests are failing, but didn't get exposed since it never runs before. |
github-actions
bot
added
docs
yuxiqian
force-pushed
the
misc/workflow-update
branch
from
02b0a70 to
2772cfa
Compare
github-actions
bot
removed
docs
|
CI failure seems irrelevant to this change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains some pretty trivial fixes on our GHA workflows:
Now, our
actions/staleworkflow closes inactive PRs with a 60 / 30 days cycle, that is to say, 60 days' inactive to label it "Stale" and 30 more days to close it. But it turns out to be too eager and has accidentally closed many useful PRs.This change has been discussed with other maintainers.
Labeler can automatically detect what files have been touched, and categorize PRs with suitable labels, based on a predefined ruleset. It's just a routine update on the rule definition.
There are really too much CI workflows scheduled to run on UTC midnight that Apache's download server could not handle (like this). Changing it to another "arbitrary" time to reduce such failure.